Skip to content

Conversation

@pllim
Copy link
Collaborator

@pllim pllim commented Aug 27, 2025

This PR addresses a little bit of #9383 , as seen in #9666 .

This round touches a lot of subpackages because I tried to do global search and replace for common offenders. Hopefully the diff is self-explanatory.

No need to run RT.

Tasks

  • If you have a specific reviewer in mind, tag them.
  • add a build milestone, i.e. Build 12.0 (use the latest build if not sure)
  • Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
    • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see changelog readme for instructions)
    • update or add relevant tests
    • update relevant docstrings and / or docs/ page
    • start a regression test and include a link to the running job (click here for instructions)
      • Do truth files need to be updated ("okified")?
        • after the reviewer has approved these changes, run okify_regtests to update the truth files
  • if a JIRA ticket exists, make sure it is resolved properly

@codecov
Copy link

codecov bot commented Aug 27, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.49%. Comparing base (58cc165) to head (d1c362b).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9777   +/-   ##
=======================================
  Coverage   82.49%   82.49%           
=======================================
  Files         366      366           
  Lines       37134    37139    +5     
=======================================
+ Hits        30633    30639    +6     
+ Misses       6501     6500    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@pllim pllim marked this pull request as ready for review August 27, 2025 17:26
@pllim pllim requested review from a team as code owners August 27, 2025 17:26
@pllim pllim requested a review from melanieclarke August 27, 2025 17:26
@melanieclarke melanieclarke added this to the Build 12.1 milestone Aug 28, 2025
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks generally reasonable! I have a few small clean up suggestions.

@pllim
Copy link
Collaborator Author

pllim commented Aug 28, 2025

Thanks for the detailed review and catching my mistakes, @melanieclarke ! Hopefully I have addressed them all. Please let me know if I miss anything.

pllim and others added 7 commits August 29, 2025 14:19
by addressing some low-hanging fruits

DOC: Fix ami_analyze description formatting

DOC: Fix ModelContainer ref and clean up devel_io_design formatting
[ci skip]

Co-authored-by: Melanie Clarke <[email protected]>
[ci skip]

Co-authored-by: Melanie Clarke <[email protected]>
and fix broken ref as pointed out by melanieclarke
from melanieclarke.

DOC: Exorcise imgmath latex warning from local build. Just use what RTD uses.
Co-authored-by: Melanie Clarke <[email protected]>
@pllim
Copy link
Collaborator Author

pllim commented Aug 29, 2025

Hopefully good enough for now. To really go clean up the docstrings real good, might need to break down by subpackage or something, because ultimately a human has to read the docstring to be sure.

Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, good enough for now! Thanks for all the fixes.

@melanieclarke melanieclarke enabled auto-merge (squash) August 29, 2025 19:18
@melanieclarke melanieclarke merged commit 328b4d3 into spacetelescope:main Aug 29, 2025
28 checks passed
@pllim pllim deleted the doc-ref-fixes-a branch August 29, 2025 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment